WebSphere Application Server for z/OS
IBM WebSphere Application Server for z/OS is one of the platform implementations of IBM's WebSphere Application Server family. The current version is Version 8.0.
The open standard interfaces supported by WAS are common across all platforms provided the version and release levels are aligned. However, the functional implementation below the open standard specification line differs between platforms. That allows the specific attributes of the platform to be exploited without jeopardizing the common programming interface at the specification level and above.
WAS z/OS Platform Exploitation
The WebSphere Application Server for z/OS V7 product has code to directly exploit the following attributes of the platform:
- WLM—is used for transaction classification, workload routing, server expansion and relative resource allocation
- SAF—products implemented behind the SAF interface (such as IBM's RACF) provide security definition and security enforcement for the product
- Cross-memory communications—shared memory buffer exchanges is at the heart of the WebSphere Optimized Local Adapters
- SMF—WAS z/OS writes SMF 120 records, including the new 120 subtype 9 introduced in WAS z/OS V7
- RRS—used for global syncpoint coordination between WAS z/OS and other participants in two-phase commit global transactions
- zAAP—specialty processors are used for Java workload to enhance the financial profile of the product
Version 7.0 "z Differentiators" ("zDiff")
Version 7.0 of WebSphere Application Server for z/OS provides five functions that are informally known as the "zDiff" functions. They represent specific exploitation of the z/OS platform. Those functions are:
- New SMF 120, Subtype 9 -- A new SMF record designed new with V7.0 that addressed many of the shortcomings of the earlier SMF records cut by WAS z/OS. It provides a unified data view of each request/response to the applications servers.
- Optimized Local Adapters -- an externalization of a pre-existing cross-memory communication feature. This allows address spaces outside of the WAS z/OS application server the ability to participate in the same cross-memory exchange that exists within a WAS z/OS cell. The Optimized Local Adapters ("OLA" or "WOLA") are bi-directional, allowing the invocation of EJB assets from outside the application server, and the invocation of services in external facilities such as CICS, batch programs, or Unix Systems Services processes.
- FRCA -- "Fast Response Caching Accelerator," is a function of the Communication Server element of z/OS. It is a low-level caching mechanism of the TCP/IP stack. An API exists so higher-level functions may exploit the caching function. The IBM HTTP Server (Domino Go version) has for many years supported the use of the API. In Version 7 of WAS z/OS the application servers support the using of the API as well. The important distinction is that with WAS z/OS the FRCA caching is seen as an external caching provider to the WAS DynaCache facility. Application elements cached to DynaCache are then pushed to the lower caching mechanism of FRCA. All the update and invalidation characteristics of DynaCache are extended down to the lower FRCA cache as well. FRCA eliminates code path to process a request when the object requested is in FRCA cache.
- Thread Hang Recovery -- A facility that attempts to interrupt Java threads in the servant region JVM when the request timer has expired. If interruption is not possible it provides a mechanism to delay the EC3 abend of the servant region, which is the way WAS z/OS refreshes a JVM. The new function provides several enhancements over prior versions of WAS z/OS: the ability to set a custom number of threads per servant JVM; the ability to set a threshold percent of threads that may be marked hung before processing an EC3 abend; and a new "excessive CPU" variable that will quiesce the WLM enclave of a thread that has exceeded a specified amount of CPU time.
- DCS/XCF -- DCS stands for "Distributed Consistency Services" and is a feature common to WAS across all platforms. It is in essence a signaling mechanism used to keep key elements of the WAS cell aware of what functions and services are available and where they exist. XCF stands for Cross-Coupling Facility and is a function of the System z and z/OS Parallel Sysplex design. DCS/XCF is a function of WAS z/OS V7 that moves the DCS signaling off the default TCP/IP transport provider and to the XCF signaling facility.
External links